Add publish command for releasing drafts and updating Homebrew tap #47
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bep
force-pushed
the
feat/publish
branch
5 times, most recently
from
46c3abc to
068bb80
Compare
This adds a new `publish` command that: 1. Publishes a draft GitHub release (sets draft: false) 2. Updates a Homebrew cask in a tap repository with the new release The Homebrew cask update finds the .pkg archive from the release archives using a path pattern matcher (consistent with how builds/archives/releases work), extracts the SHA256 from the checksums file, and commits the cask file to the tap repository. Co-Authored-By: Claude Opus 4.5 <[email protected]>
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #47 +/- ##
===========================================
+ Coverage 16.86% 65.44% +48.57%
===========================================
Files 36 39 +3
Lines 2182 2616 +434
===========================================
+ Hits 368 1712 +1344
+ Misses 1764 696 -1068
- Partials 50 208 +158 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
- Update all.txt with publish assertions - Add dedicated publish.txt test for homebrew cask functionality Co-Authored-By: Claude Opus 4.5 <[email protected]>
Instead of parsing the checksums file in the publish command, store SHA256 values directly in BuildArchPath during the release step. This makes the checksum data available programmatically and avoids fragile file parsing. - Add SHA256 field to BuildArchPath struct - Update CreateChecksumLines to return ChecksumResult with map - Update release command to populate SHA256 in ArchsCompiled - Simplify publish command to use archPath.SHA256 directly Co-Authored-By: Claude Opus 4.5 <[email protected]>
bep
force-pushed
the
feat/publish
branch
3 times, most recently
from
0d8416b to
17e461c
Compare
Follow the archives pattern: top-level publish_settings for shared defaults and a publishers slice where each entry can match specific releases via paths and has its own type (built-in or plugin). - Add internal/publish/publishformats package with Format enum - Rewrite publish_config.go with Publisher struct and PublishType - Add Publishers field to Config struct - Update core.go to compile publisher -> release mappings - Rewrite publishcmd to iterate over publishers - Update test scripts and hugoreleaser.yaml Built-in publisher types: - github_release: Undrafts the GitHub release - homebrew_cask: Updates Homebrew cask file - _plugin: External plugin (future) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new
publishcommand that:The Homebrew cask update points to the universal macOS pkg and extracts
the SHA256 from the checksums file generated during release.
Co-Authored-By: Claude Opus 4.5 [email protected]